One-off - Mobile app

This flow is followed by merchants who wish to integrate the payment service offered by Maypay into their native app. The use cases that best fit this flow are described in Mobile app - Android SDK and Mobile app - iOS SDK.

caution

A discount of 100% off the gross amount of the purchase should be applied to amounts associated with winning payouts. The amount is in fact paid by Maypay while the user does not pay. The amount paid by Maypay for each winning outcome is in the form of a reversal from the commissions retained by Maypay and allocated to the prize pool.

Read more

APIs required

• Create Merchant Payment Request (Flow: Mobile App)
• Cancel Merchant Payment Request
• Get Merchant Payment Request

tip

cancelMerchantPaymentRequest and getMerchantPaymentRequest are not shown in the sequence diagram below because they are optional. With the former the merchant can request the cancellation of a pending request, while with the latter he can request the data and current status of the payment request.

caution

The last step in the sequence diagram is only possible if the ecommerce app declares its universal link (iOS) or its app link.

For further information, please refer to the guide Universal Links for Developers (iOS) or Handling Android App Links

Sequence Diagram

sequenceDiagram participant MA as Maypay App participant MS as Maypay Server participant ES as eCommerce Server participant EA as eCommerce App rect rgb(255, 255, 255) EA->>ES: Start Checkout activate ES ES->>MS: POST createMerchantPaymentRequest - flow Mobile App activate MS MS->>ES: 201 CREATED - merchant deactivate MS ES->>EA: payment request id deactivate ES EA->>MA: MaypaySDK.openMaypay - payment request id MA->>MS:GET Payment Request activate MS MS->>MA: payment request deactivate MS MA->>MS:confirm payment request activate MS MS-->>MA: payment result MS-->>ES: payment result via callback url deactivate MS ES->>ES: order completed ES->>EA: order completed MA->>EA: open eCommerce App using redirectURL end